<html>
	<head>
  		<meta http-equiv="Content-Type"
 		content="text/html; charset=iso-8859-1">
	 	 <meta name="Title" content="CISC 275 Software Engineering I">
 		 <meta name="GENERATOR"
		 content="Mozilla/4.75 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
		<link href="cisc105.css" rel="stylesheet" type="text/css" media="all">
  		<title>CISC 275 Software Engineering I</title>
	</head>

	<body>
		<div id="container">


		<div id="banner">
			<img class="key" src="ud.gif" align="right">
			<h1>CISC 275 Software Engineering I</h1>
			<h1>Fall 2010<br></h1>
		</div>

			<div id="content">
This document is subject to change. Check it for updates at least
weekly during the semester.<br>
			<br>
			
Instructor: Terry Harvey
<br>Office:  408 Smith Hall<br>Office hours: Tues 1:30 - 3:30, Fri 11
- 1<br>
Email: tharvey at udel.edu
<br>
Phone: don't phone, email!<br>

			<p>TA: Charlie Greenbacker</p>
				<p>email: charlieg at udel.edu</p>
				<p>Office Hours: </p>
				<p>&nbsp;<br>
				</p>
				<hr width="75%">
				<h2>Useful Links</h2>

				<ul>
					<li><a href="labs/">Lab Assignments</a>
					<li><a href="http://www.cis.udel.edu/~charlieg/Teaching.html">Charlie's website</a>

					<li><a href="examples/">Example programs </a>from class
					<li><a href="resources/">Resources</a>
					<li><a href="readings.html">Readings</a>

					<li><a href="standards.html">Assignment Submission Standards</a>
					<li><a href="whatisaTA.html">What is a TA?</a>
				</ul>


<p>Text: Program Development in Java, Barbara Liskov (with John Guttag)<br>
					ISBN-10: 0201657686<br>
					ISBN-13: 978-0201657685</p>

<p><span style="color: black;"></span></p>
<p></p>
				<p><span style="color: black;"></span></p>
				<p><span style="color: black;"></span></p>
				<hr width="75%">
				<p>This class web page is where you find labs, projects, examples, hints, changes to the schedule, etc. Check here every week, or more frequently. Depending on which browser you use, you may need to hit &quot;reload&quot; or &quot;refresh&quot; to see new material.</p>


				<h3>Important dates, subject to change:</h3>
				<table width="553" border="1" cellspacing="2" cellpadding="0">
					<tr>
						<td>10/13</td>
						<td>Midterm Exam</td>
					</tr>									<tr>
						<td>11/17</td>
						<td>Second Midterm Exam</td>
					</tr>					<tr>
						<td>d</td>
						<td>UML use cases,
				class and sequence diagrams</td>
					</tr>

					<tr>
						<td>d</td>
						<td>First code review:
				classes, stubs, compiles</td>
					</tr>
					<tr>
						<td>d</td>
						<td>Second code review: simple use case w/GUI</td>

					</tr>
					<tr>
						<td>d </td>
						<td>Project 2 final
				code review</td>
					</tr>
					<tr>
						<td>d </td>

						<td>Final Presentations</td>
					</tr>
					
					<tr>
						<td>Thurs 12/16</td>
						<td>Final Exam 7 - 9 PM</td>
					</tr>
					<tr>

						<td></td>
						<td></td>
					</tr>
				</table>


<h1>Course Objectives</h1>
				
				<p>This course is designed to introduce students to a variety of tools and ways of thinking about software and software development. Topics to be introduced include</p>
				<p class="MsoNormal" style="margin-left: 0.75in; text-indent: -0.25in;"><span
 style="" times="" new="" roman=""><span style="" times="" new=""
 roman=""></span></span></p>

				<ol>
					<li>GUI programming
					<li>UML diagrams
					<li>Object-oriented style
					<li>Modular design
					<li>Method-level specification
					<li>Automated testing
					<li>simple Design Patterns
					<li>simple version control
					<li>using an IDE
					<div id="content">
						<ol>
							
						</ol>

					</div>
					<li>Working in teams

					<li>Making presentations
					<li>Evaluation of code for
				</ol>
			</div>
			<ul>
				<div id="content">
					<ul>
						<ul>

							<li>modularity
							<li>separation of concerns
							<li>generality
							<li>reuseability
						</ul>
					</ul>
				</div>
			</ul>
			<div id="content" align="left">
				<p>At the conclusion of this course students should be more comfortable with the design and implementation of software projects requiring multiple authors, and should be well-positioned to tackle advanced versions of these same topics in Software Engineering II, CISC475.</p>

			</div>
			<div id="content">
				<h1>Lecture</h1>
				We will cover a wide variety material in this
			course, not all of which is in the textbook. Attending lecture is essential to
			learn the material and to interact with class
			members, teammates, and the professor.
				<h1>Lab</h1>
				Labs will come out each Thursday, and be
				due the following Wednesday at midnight
				on Sakai unless otherwise
				specified. Also, your TA will collect
				paper copies of the lab (for ink
				grading) at the start of your next lab.  <b>Bring your printed lab with you to lab.</b>
				<p>After you submit a lab, I will give detailed answers to questions about the lab. For this reason, it is important that you submit on time. Late assignments will receive a 25 percent penalty immediately, and an additional ten percent each 24 hours. No exceptions will be made for traffic, dead disks, fried monitors, political protests, etc. Please work on your assignments early and often.</p>

				<p>Labs may be done alone or in groups, We will specify which for each lab.  If you work in a team, 1) put <b>all</b> the names on the assignment; 2)<b> every</b> team member must submit electronically; 3) only submit <b>one</b> paper copy.</p>
				<h1>Participation</h1>
				There will be many opportunities to participate in class. Participation includes asking questions, answering instructor questions, and being an active and constructive party when asked to work with other students in class. Speak up! It's ten percent of your grade. If you have remarkable difficulty speaking in class, see me during the first week of class to discuss alternative assignments.
				<p>Finally, ten percent of your grade will be based on your presentations of material in class. When you are part of a team, be sure that you present material every time the team does. Know the material well enough that you are not reading. We'll go over lots of other presentation points.</p>

				<h1>Grading</h1>
				<p>10% Labs</p>
				<p>10% Presentations</p>
				<p>15% Midterm</p>
				<p>10% Project 1 (includes all phases) </p>
				<p>30% Project 2 (includes all phases) </p>
				<p>15% Cumulative Final</p>
				<p>10% Participation </p>

				<p>At the end of the semester, all grades  will be taken into account by the instructor in determining whether or not to apply a curve of some kind. Under no circumstance will grades be curved &quot;down&quot;, but there is no guarantee that grades will be curved up.</p>
				<h1>Projects</h1>
				<p>This semester's projects will
				involve working in teams. The project grade will be
				composed of a number of parts,
				including multiple presentations, all
				parts of the software engineering
				cycle, quality of teamwork, and final
				presentation. 
				<h1>Assignments</h1>
				<p>Typically, labs and projects will be graded by the TA, exams by the instructor. Once an assignment is returned, you have a week to request that your grade on the assignment be re-examined. Submit the assignment to the person who graded it along with a cover sheet explaining where you think you should be credited with additional points and why. If you submit for re-grading to the TA and are not satisfied with the result, you may re-submit to the instructor, but be forewarned that historically this option has not met with much success.</p>
				<p>See the separate document on <a
 href="standards.html">Assignment
Standards.</a></p>
				<h1>Academic Honesty</h1>

				<p>I expect my students to uphold the
				highest standards of academic honesty,
				as described in the University Code of
				Conduct at <a href="http://www.udel.edu/stuguide/09-10/code.html">http://www.udel.edu/stuguide/09-10/code.html</a></p>
				<p>Any violations will be referred to
				the Office of Academic Conduct.</p>
				<p><b>NOTES:</b></p>
				<p><b>Quizzes and exams are not team activities, and must be written solely by you without assistance of any kind.</b></p>
				<p><b>Teams must work independently of other teams. Do not share work or code between teams; this is a violation of the Academic Honesty policy.</b></p>
				<p><b>If you are ever in doubt about whether some activity is permitted, do not do it until you have asked the professor and received clarification.</b></p>

				<p></p>
				<p></p>
				<p></p>
			</div>
		</div>
</body>
</html>
